In some cases ‘access’ can be a multi-layered monster that needs a separate subproject to deliver.

Steps in delivering the right type of access at the right moment in time may include executing per resource, per country:

• Capgemini’s HR process to assign a Capgemini personnel identification number
• The Client’s HR process to assign a Client’s personnel identification number
• Capgemini’s IT or infrastructure services partner process to assign an user id and password in Capgemini’s active directory
• The Client’s IT or infrastructure services partner’s process to assign an user id and password in the Client’s active directory
• The Client’s IT or infrastructure services partner process to set-up a Virtual Desktop
• The Client’s IT or infrastructure services partner process to assign the needed software to that Virtual Desktop
• The Client’s IT or infrastructure services partner process to assign the resource to his/her Virtual Desktop
• The Client’s IT or Client’s infrastructure services partner process to give the resource the right software and the right level of access in that software in his/her Virtual Desktop
• The Client’s and/or Capgemini’s IT or infrastructure services partner’s process to grant access via all the related components in the network connection between the Client and Capgemini
• The Client’s IT or Client’s infrastructure services partner process to give the resource the right level of access to systems in scope
• The Client’s business process to authorize the resource to access the systems, software components and/or the data in scope
• The countries’ local or regional government authorities to authorize Capgemini and/or specific resources to access the systems, software components and/or the data in scope demanding:
  • • Positive result of investigation in the resource’s legal history and background
    • Signed data-privacy agreements with all parties involved
    • Signed non-disclosure agreements
    • Signed confidentiality agreements
• The Client’s IT or Client’s infrastructure services or the Client’s technical application management partner process to give the resource the right level of authorization on the software components in scope.

The Service Engagement Staff work stream team needs to find all access layers and needs to find all processes to apply so that the resources can receive the right level of access at the right moments in time. The Service Engagement Staff work stream will set-up the Access Tracker artifact based on the requirements per resource and the different layers of access to distinguish.

Regarding ‘access’, the Service Engagement Staff work stream and the Technology And Infrastructure work stream often have to work closely together. In case of ‘access’ being a multi-layered monster as described above, a separate subproject might be needed that could either reside under the Service Engagement Staff work stream or under the Technology And Infrastructure work stream, wherever the main focus lies. The Service Engagement Staff work stream would fit better when the focus is on the Human Resource process or the Client business process, the Technology And Infrastructure work stream fits better when there are a lot of technical hurdles to take.